…(fork a); PDR-0011

Owner selected 'federation integration hardening' and the offline-contract-hardening
fork after a per-seam audit found the seams contract-shaped but never live-proven,
with a silent-drift risk on the SHIPPED /git/renames seam (its contract test asserts
against _parse_like_loomweave, a legis-authored mock of Loomweave's Rust parser).

- PDR-0011: bet = G16 (replace the self-referential rename mock with a committed
  two-way shared-vector file + author it for Loomweave) + G8 (backfill resolve
  guards). Excludes G2 (Loomweave-blocked), G12/oracles (live-fire), Path B (strategy).
- roadmap: promoted the bet Now; residual forks kept in Next. metrics: new guardrail
  (rename-parser conformance vector-pinned, not self-referential — currently BREACHED).
- Escalation flagged, not enacted: Loomweave co-committing the shared vectors.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

check_changed_format.py decodes git's -z output with errors="surrogateescape",
but --print-only then wrote the path list through print() to a strict UTF-8
stdout, raising UnicodeEncodeError on a non-UTF-8 .py filename. Emit the list
via sys.stdout.buffer with the matching surrogateescape handler instead. Fixes
the red test_changed_format_gate_uses_current_existing_paths; full suite green
(1687 passed, 12 skipped).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Branch-review remediation (1 MEDIUM + 1 LOW).

MEDIUM: the Codex TOML reader caught (TOMLDecodeError, UnicodeError) but not
RecursionError/MemoryError, so a sub-1-MiB but pathologically nested
config.toml crashed `legis doctor` with an uncaught RecursionError instead of
the documented fail-closed [operator] handling (invariant 5, and a doc-claim
contradiction). Catch both and map to a fail-closed "nesting exceeds safe
limits" error, mirroring the project-JSON reader's nesting guard.

LOW: pin the new python `-m plainweave.mcp_server` launcher's two reject paths
(a non-python command carrying the module args; a python launcher for a
non-plainweave module) so a future regression that loosened the exact
args[:3] match to args[:2] would be caught.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Branch-review remediation (LOW). A hard kill between fsync(temp) and
os.replace during a binding repair or MCP registration write leaves an
orphaned `.mcp.json.<hex>.tmp` / `.mcp.json<rand>.tmp` in the project root
that the finally-block cleanup cannot remove on SIGKILL/power loss. Add
`/.mcp.json*.tmp` to the Legis .gitignore rule set so crash residue never
surfaces as a tracked change; doctor --fix adds the rule to existing installs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Cut the 1.5.0 release line from the Plainweave doctor-binding feature work.
- version: pyproject + legis.__version__ 1.4.0 -> 1.5.0
- CHANGELOG: promote the [Unreleased] "legis doctor Plainweave binding" Added
  entry under a new [1.5.0] — 2026-07-12 heading; add the v1.4.0...v1.5.0
  compare link and retarget [Unreleased].
- README: status line and the "1.5.x line" continuity reference.

Includes the branch-review remediation carried on the release branch: the
Codex config.toml RecursionError fail-closed fix, the .mcp.json repair
temp-file ignore rule, the surrogate-safe changed-format gate, and the
Plainweave python-launcher reject-path test pins.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>